📢 Type of change

• Bugfix

📜 Description

On React Native + Hermes (including Expo OTA / expo export Hermes bundles), plain JS exception events often ship without debug_meta.images, even when Metro injected the Debug ID premodule (_sentryDebugIds) and the matching artifact bundle was uploaded with that Debug ID.

The core prepareEvent pipeline attempts this via applyDebugIds → applyDebugMeta, but that path re-parses the premodule Error().stack and requires an exact filename match against the exception frames. That match is fragile for Hermes premodule stacks, so filenameDebugIdMap ends up empty and no debug_meta is attached.

Profiling already solves the same problem robustly via getDebugMetadata() (profiling/debugid.ts): it reads _sentryDebugIds directly and stamps a single sourcemap image with the canonical bundle code_file (app:///index.android.bundle / app:///main.jsbundle) — no stack reparse. That helper was not wired into the error event pipeline.

This PR adds a default debugMetaIntegration that reuses getDebugMetadata() to stamp debug_meta.images on error events. Key details:

• Scoped to error events (event.type === undefined) — transactions, profiles and other event types are untouched.
• Idempotent against core. Core runs applyDebugIds (sets frame.debug_id) before event processors and applyDebugMeta (stamps images) after them. The integration detects a successful core match via frame.debug_id and backs off, so core's own stamp is not duplicated. When core fails to match (the bug case), the integration fills the gap.
• Defensive dedupe by debug_id, and preserves unrelated pre-existing images (e.g. native images added by nativeLinkedErrors).
• Registered right after createReactNativeRewriteFrames() so the canonical bundle filename is already in place.

💡 Motivation and Context

Without debug_meta, backends fall back to release + filename matching. RN/Expo rewrites every JS frame to the same canonical filename, and OTA updates keep the native release, so the native build's Hermes map can be applied to OTA bytecode → wrong files/lines. The missing debug_meta is an SDK-side gap regardless of backend.

Fixes #6480

💚 How did you test it?

• Added test/integrations/debugmeta.test.ts covering: stamping on error events, no-op when no Debug ID, skipping non-error events, backing off when core matched, and preserving pre-existing images.
• Added tests that reproduce the core prepareEvent ordering (applyDebugIds → event processor → applyDebugMeta) and assert exactly one image results whether core succeeds or fails — guarding against a duplicate-image regression.
• Regenerated the API report for the new public debugMetaIntegration.

📝 Checklist

• I added tests to verify changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.
• No breaking changes.

🔮 Next steps

• Confirm naming (debugMetaIntegration) — the mechanism is RN/Hermes-specific (single bundle per platform); a more specific name could be used if preferred.

🤖 Generated with Claude Code